A GNS running on a Bastion host server can be configured to send notifications to alert users that a failover is occurring within the redundancy environment. The GNS sending the notifications is not configured for redundancy. Several failover-related attributes are passed from the redundant RSM to the reporting GNS, which in turn resolve to the following dynamic tokens:
| GNS Token | Description |
|---|---|
|
%failover_active_domain% |
The active domain. |
|
%failover_comment% |
The comment associated with the failover. |
|
%failover_scope% |
The type or scope of the failover. For example, "Local" or "Data Center." |
|
%failover_set_name% |
The name of the failover set configured in the redundancy definition:
|
|
%failover_standby_domain% |
The standby domain. |
|
%failover_type% |
This token will return the type of failover, whether soft or hard. |
|
%initiating_user% |
The username of the person who initiated the failover. |
|
%master_rsm% |
The RSM where the failover was triggered. This is usually the standby RSM that will become the active RSM. |
|
%services_in_failover% |
The CygNet services participating in the failover. Since there is usually more than one, this will return as a comma delimited list. |
|
%time% |
This token will return the time at which the failover was first triggered. |
These tokens can be used to configure a notification message for a GNS Event record in the GNS message editor. For example, you could configure the following message to be sent from the GNS when a failover is triggered:
|
%initiating_user% has initiated a %failover_type% failover for the %failover_set_name%. This is a %failover_scope% failover between the %failover_active_domain% and %failover_standby_domain% domains.
Services affected: %services_in_failover%
Reason: %failover_comment% |
The GNS will substitute each token with the appropriate value, resulting in the following notification. (The dynamic value is shown in bold.)
|
ABC\Bob.Smith has initiated a Soft failover for the Houston – Production Network. This is a Local failover between the 5412 and 5413 domains.
The services affected are: CYGNET.UIS, CYGNET.DDS, CYGNET.FAC, CYGNET.PNT, CYGNET.VHS
Reason: The CPU was running high on the active server so I moved a couple services to the standby domain to try and isolate the cause. |
Note that the tokens are not available for direct selection from the token lists in the GNS message editor, but you can type the tokens manually and they will be recognized.
The only other tokens that can be used in these types of notifications messages are those in the Notification Timeout category (Expiration time and Time in seconds remaining). None of the other tokens (Notification Current Values, Current Values, Point, or Facility) will work for this type for message.
Once you have configured the GNS Event notification and message, you can specify the Reporting GNS that will send the notification and associate the appropriate GNS event with each step in the redundancy workflow from the CygNet Redundancy Editor as shown below.
|
|
|
